ES-2748,ES-2530 - Updated description for eSignet test cases#1623
ES-2748,ES-2530 - Updated description for eSignet test cases#1623zesu22 merged 6 commits intomosip:developfrom
Conversation
Signed-off-by: Prathmesh Jadhav <[email protected]>
Signed-off-by: Prathmesh Jadhav <[email protected]>
WalkthroughConsolidates CSRF token fetching to a single early point in the test runner, moves/removes redundant fetches, adds/adjusts DB cleanup queries, introduces a new UserInfo Consent No Capture test with Handlebars templates, and updates several Consent No Capture test descriptions and template paths. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In
`@api-test/src/main/resources/esignet/OTPAuthFactorFlow/ConsentNoCapture/UserinfoConsentNoCapture/UserInfoConsentNoCapture.yml`:
- Around line 10-11: This file duplicates templates in the old
"UserinfoConsentNoCapture" folder; either remove the outdated directory or move
this YAML into the PascalCase "UserInfoConsentNoCapture" directory and update
its inputTemplate/outputTemplate references to use the
"UserInfoConsentNoCapture/UserInfoConsentNoCapture" and
"UserInfoConsentNoCapture/UserInfoConsentNoCaptureResult" paths respectively so
only the PascalCase folder remains and no duplicate configurations exist.
In
`@api-test/src/main/resources/esignet/OTPAuthFactorFlow/ConsentNoCapture/UserInfoConsentNoCapture/UserInfoConsentNoCapture.yml`:
- Around line 1-15: Remove the misnamed duplicate directory
"UserinfoConsentNoCapture" (lowercase i) and its YAML/test files so only the
correctly named "UserInfoConsentNoCapture" remains; ensure the single remaining
test configuration retains the uniqueIdentifier
TC_ESignet_UserInfoConsentNoCapture_01 and continues to reference the
input/output templates at
esignet/OTPAuthFactorFlow/ConsentNoCapture/UserInfoConsentNoCapture/UserInfoConsentNoCapture
and ...UserInfoConsentNoCaptureResult to avoid duplicate registration/conflicts
during test discovery.
...net/OTPAuthFactorFlow/ConsentNoCapture/UserinfoConsentNoCapture/UserInfoConsentNoCapture.yml
Show resolved
Hide resolved
...net/OTPAuthFactorFlow/ConsentNoCapture/UserInfoConsentNoCapture/UserInfoConsentNoCapture.yml
Show resolved
Hide resolved
...net/OTPAuthFactorFlow/ConsentNoCapture/UserInfoConsentNoCapture/UserInfoConsentNoCapture.yml
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In
`@api-test/src/main/resources/esignet/OTPAuthFactorFlow/ConsentNoCapture/GenTokenConsentNoCaptureNegTC/GenTokenConsentNoCaptureNegTC.yml`:
- Line 5: Update the misleading description strings in the
GenTokenConsentNoCaptureNegTC YAML: replace the phrase "Verify successful token
generation … using in invalid redirect uri" (and the similar description at the
other occurrence) with wording that reflects this is a negative test expecting
an invalid_request error and fix the typo "using in invalid" → "using an
invalid"; locate the description fields inside the GenTokenConsentNoCaptureNegTC
test block and change them to something like "Verify token request with an
invalid redirect_uri returns invalid_request error" so the intent and expected
failure are clear.
Summary by CodeRabbit
Tests
Bug Fixes
Chores